Skip to content

Declare "module" in package.json #282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2019

Conversation

maisano
Copy link
Contributor

@maisano maisano commented Feb 6, 2019

What:

This change exposes the ESM version of the build, in the same fashion that the ES modules build is declared in dom-testing-library.

Why:

The ESM build is currently generated and distributed upon publish, though it is not exposed via package.json. My admittedly selfish use case for this is in having better heuristics around some linting rules (namely import/named).

How:
• Added the module field to package.json, pointing it at the path of the built artifact

Checklist:

  • Documentation (N/A)
  • Tests (N/A)
  • Ready to be merged
  • Added myself to contributors table

&c.:

Thanks for this library–it's great! Let me know if there's anything I overlooked or you would like to see changed.

This change exposes the ESM build of react-testing-library.
@kentcdodds kentcdodds merged commit 74a6eba into testing-library:master Feb 6, 2019
@kentcdodds
Copy link
Member

Thanks!

@kentcdodds
Copy link
Member

🎉 This PR is included in version 5.5.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants